This repository was archived by the owner on Jan 26, 2021. It is now read-only.
Allow equalTo queries with Parse.Object pointers#47
Open
mikemintz wants to merge 1 commit intoparse-community:masterfrom
Open
Allow equalTo queries with Parse.Object pointers#47mikemintz wants to merge 1 commit intoparse-community:masterfrom
mikemintz wants to merge 1 commit intoparse-community:masterfrom
Conversation
|
it seems to me that when I apply this patch, I end up with the key on this.data containing the pointer which doesn't have the fields from the flattened object. |
|
Actually that was because I was keeping a list of objectIds as strings in an array as a field (edit: rather, a column). This fix does work if I have userThing: (new Parse.Query('Things'))
.equalTo('user', Parse.User.current())
.include('field1')
.include('nestedfield2')
.limit(1)where before this, the mutation wouldn't propagate without a page refresh. |
mikemintz
force-pushed
the
equalto-parse-pointers
branch
from
154bb22 to
75cbb40
Compare
mikemintz
force-pushed
the
equalto-parse-pointers
branch
from
75cbb40 to
ec0d7b5
Compare
|
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed. |
|
I applied this patch and it seems to fix my problem. Hope this can get merged into master soon! Thanks @mikemintz |
ghost
added
the
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This resolves #37
This allows an equalTo constraint to use a Parse.Object pointer instance and be automatically updated with the result of a mutation. Previously it would only work with flattened parse objects, because it checked
.objectIdinstead of.id. Now it allows for either.